Description

Implements #1578.
This PR only adds a /stackable/libjvmkill.so file to the existing java-base image, so it's guaranteed to be non-breaking.
This should already enable customers to use it (see SUP-354).

After the 26.7 release we will actually start to use the file in trino-operator by setting -agentpath:/stackable/libjvmkill.so

I did a quick sanity check to make sure we can at least load the agent (I did not test if it improves the JVM situation):

---
apiVersion: trino.stackable.tech/v1alpha1
kind: TrinoCluster
metadata:
  name: simple-trino
spec:
  image:
    productVersion: "481"
    custom: foo:bar
    pullPolicy: IfNotPresent
  clusterConfig:
    catalogLabelSelector:
      matchLabels:
        trino: simple-trino
  coordinators:
    roleConfig:
      listenerClass: external-unstable
    jvmArgumentOverrides: &jvmArgumentOverrides
      add:
        - -agentpath:/stackable/libjvmkill.so
    roleGroups:
      default:
        replicas: 1
  workers:
    jvmArgumentOverrides: *jvmArgumentOverrides
    roleGroups:
      default:
        replicas: 1

Definition of Done Checklist

Please make sure all these things are done and tick the boxes

• Changes are OpenShift compatible
• All added packages (via microdnf or otherwise) have a comment on why they are added
• Things not downloaded from Red Hat repositories should be mirrored in the Stackable repository and downloaded from there
• All packages should have (if available) signatures/hashes verified
• Add an entry to the CHANGELOG.md file
• Integration tests ran successfully

boil build <IMAGE> --image-version <RELEASE_VERSION> --strip-architecture --load
kind load docker-image <MANIFEST_URI> --name=<name-of-your-test-cluster>